Method and apparatus for using locale-specific grammars for speech recognition

ABSTRACT

One embodiment of the present invention provides a system that facilitates recognizing voice input. During operation, the system receives a document that includes a specification of a datatype for which there exists a predefined grammar. The system also obtains a locale attribute for the datatype, wherein the locale attribute identifies a version of a language that is spoken in a locale. Next, the system uses the locale attribute to lookup a locale-specific grammar for the datatype, and then communicates the locale-specific grammar to a speech recognition engine, thereby allowing the speech recognition engine to use the locale-specific grammar to recognize voice input for the datatype.

RELATED APPLICATION

[0001] This application hereby claims priority under 35 U.S.C. §119 to U.S. Provisional Patent Application No. 60/440,309, filed on 14 Jan. 2003, entitled “Concatenated Speech Server,” by inventor Christopher Rusnak (Attorney Docket No. OR03-01301PSP), and to U.S. Provisional Patent Application No. 60/446,145, filed on 10 Feb. 2003, entitled “Concatenated Speech Server,” by inventor Christopher Rusnak (Attorney Docket No. OR03-01301PSP2). This application additionally claims priority under 35 U.S.C. §119 to U.S. Provisional Patent Application No. 60/449,078, filed on 21 Feb. 2003, entitled “Globalization of Voice Applications,” by inventors Ashish Vora, Kara L. Sprague and Christopher Rusnak (Attorney Docket No. OR03-03501PRO).

[0002] This application is additionally related to a non-provisional patent application entitled, “Structured Datatype Expansion Framework,” by inventors Ashish Vora, Kara L. Sprague and Christopher Rusnak, filed on the same day as the instant application (Attorney Docket No. OR03-03501).

[0003] This application is additionally related to a non-provisional patent application entitled, “Method and Apparatus for Facilitating Globalization of Voice Applications,” by inventor Ashish Vora, filed on the same day as the instant application (Attorney Docket No. OR03-03701).

BACKGROUND

[0004] 1. Field of the Invention

[0005] The present invention relates to voice interfaces for computer systems. More specifically, the present invention relates to a method and an apparatus that facilitates globalizing voice applications.

[0006] 2. Related Art

[0007] Globalization of software applications is emerging as a business necessity in today's increasingly interconnected marketplace. This interconnectedness, coupled with a soft economy, provides a valuable opportunity for companies that can efficiently and effectively provide their software to the largest audience. Far too often, globalization is an afterthought in the application development cycle—composed of ad hoc processes and frameworks grafted onto the final stages of the implementation process. Companies that undertake a globalization effort in this ad hoc fashion are likely to rewrite their applications for each language, or worse, fail to ship software in multiple languages altogether.

[0008] Nowhere is this more evident than in the speech technology world. The unique challenges posed by voice application development are daunting even for single-language development. Adding multiple languages to the mix and trying to maintain the ideal of a single code base and simultaneous shipment for all languages only makes the task harder. A variety of methods and processes exist to facilitate globalization of screen-based applications, but unfortunately, these methods and processes fall short (on their own) to address the needs of voice applications developers.

[0009] Hence, what is needed is a completely new voice globalization framework to help mitigate the complexity associated with these tasks.

SUMMARY

[0010] One embodiment of the present invention provides a system that generates voice output for an application. During operation, the system receives a symbolic representation of data to be outputted from the application, wherein the symbolic representation is locale-independent. The system also obtains a locale attribute that identifies a version of a language that is spoken in the locale. Next, the system expands the symbolic representation into a fully articulated locale-specific textual representation of the data, and then associates the textual representation with one or more audio files containing locale-specific voice output corresponding to the textual representation.

[0011] In a variation on this embodiment, the system also outputs the audio files to a user. This can involve sending references to the audio files from an application server to a voice gateway, and then allowing the voice gateway to output the audio files to the user.

[0012] In a variation on this embodiment, upon receiving a voice input from the user, the system interprets the voice input using a locale-specific grammar.

[0013] In a variation on this embodiment, the locale attribute is encoded in a Voice eXtensible Markup Language (VoiceXML) document that contains a locale-independent representation of how voice output is to be presented to a user. It also contains a locale-independent representation of how a voice input is to be received from the user.

[0014] In a variation on this embodiment, obtaining the locale attribute involves receiving the locale attribute as an application parameter, possibly associated with a particular user.

[0015] In a further variation, the VoiceXML document is obtained by translating a Multi-channel eXtensible Markup Language (MXML) document into the VoiceXML document, wherein the MXML document can also be translated into other markup languages, such as HyperText Markup Language (HTML).

[0016] In a variation on this embodiment, associating the textual representation of the data with the audio files involves matching the largest possible substrings of the textual representation with corresponding audio files from a library.

[0017] In one embodiment of the present invention, the locale attribute includes a language code that identifies the language, and a region code that identifies a geographic region in which a locale-specific version of the language is spoken.

[0018] One embodiment of the present invention provides a system that facilitates recognizing voice input. During operation, the system receives a document that includes a specification of a datatype for which there exists a predefined grammar. The system also obtains a locale attribute for the datatype, wherein the locale attribute identifies a version of a language that is spoken in a locale. Next, the system uses the locale attribute to lookup a locale-specific grammar for the datatype, and then communicates the locale-specific grammar to a speech recognition engine, thereby allowing the speech recognition engine to use the locale-specific grammar to recognize voice input for the datatype.

[0019] In one embodiment of the present invention, the document that includes the specification of the datatype is a Voice eXtensible Markup Language (VoiceXML) document.

[0020] In one embodiment of the present invention, obtaining the locale attribute involves obtaining the locale attribute from the VoiceXML document.

[0021] In a variation on this embodiment, the locale attribute is encoded in an MXML document which is used to generate a Voice eXtensible Markup Language (VoiceXML) document.

[0022] In a variation on this embodiment, the locale attribute can be encoded in any one of a number of different application markup languages, such as HTML, XML, WML and MXML.

[0023] In a variation on this embodiment, obtaining the locale attribute involves receiving the locale attribute as an application parameter, possibly associated with a particular user.

[0024] In one embodiment of the present invention, the locale-specific grammar identifies a standard set of phrases to be recognized by the speech recognition engine while receiving voice input for the datatype.

[0025] In one embodiment of the present invention, the locale-specific grammar associates a phrase that can be spoken with a corresponding semantic meaning.

[0026] In one embodiment of the present invention, communicating the locale-specific grammar to the speech recognition engine involves communicating a reference to the speech recognition engine, wherein the reference specifies where the locale-specific grammar can be retrieved from.

[0027] In one embodiment of the present invention, communicating the locale-specific grammar to the speech recognition engine involves incorporating the grammar “in-line” into a VoiceXML document, and then communicating the VoiceXML document to the speech recognition engine.

[0028] In one embodiment of the present invention, the locale attribute includes a language code that identifies the language, and a region code that identifies a geographic region in which a locale-specific version of the language is spoken.

[0029] One embodiment of the present invention provides a system that expands a symbolic representation of a data item into a locale-specific textual representation of the data item. The system operates by first receiving a locale-independent symbolic representation of the data item. Next, the system obtains a locale attribute that identifies a version of a language that is spoken in a locale, and then expands this symbolic representation of the data item into the locale-specific textual representation of the data item.

[0030] In a variation of this embodiment, the locale is received along with the data item.

[0031] In a further variation, receiving the data item includes receiving expansion attributes for controlling expansion of the data item.

[0032] In a further variation, the system selects an expander for expanding the data item. This expander is selected based upon the locale attribute.

[0033] In a further variation, the expander accepts the data item, the locale attribute, and the expansion attributes and generates the locale-specific textual representation of the data item as an output.

[0034] In a further variation, the locale attribute and the expansion attributes are received as part of a conversion command.

[0035] In a further variation, the locale attribute and the expansion attributes are elements of a cascading style sheet.

BRIEF DESCRIPTION OF THE FIGURES

[0036]FIG. 1 illustrates a system that provides a transformation framework from an MXML document in accordance with an embodiment of the present invention.

[0037]FIG. 2 illustrates a voice gateway in accordance with an embodiment of the present invention.

[0038]FIG. 3A illustrates mechanisms involved in generating voice output for an application in accordance with an embodiment of the present invention.

[0039]FIG. 3B illustrates an expansion mechanism in accordance with an embodiment of the present invention.

[0040]FIG. 4 presents a flow chart illustrating the process of generating voice output in accordance with an embodiment of the present invention.

[0041]FIG. 5 illustrates the process of receiving voice input in accordance with an embodiment of the present invention.

[0042]FIG. 6 illustrates how voice transformers are constructed in accordance with an embodiment of the present invention.

[0043]FIG. 7 presents a flow chart illustrating how the system is configured to receive voice input in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

[0044] The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

[0045] The data structures and code described in this detailed description are typically stored on a computer readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs), and computer instruction signals embodied in a transmission medium (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, such as the Internet.

[0046] Transformation Framework

[0047]FIG. 1 illustrates a system that provides a transformation framework 102 within an application server 105 in accordance with an embodiment of the present invention. Transformation framework 102 receives a Multi-channel extensible Markup Language (MXML) document 104 and translates the MXML document 104 into other markup languages, such as Hypertext Markup Language (HTML), extensible Markup Language (XML), Wireless Markup Language (WML), and Compact Hypertext Markup Language (cHTML).

[0048] These other markup languages can be used to communicate with different devices. For example, VoiceXML can be used to communicate with telephones 116 and 118 through voice gateways 106 and 108, which allow VoiceXML documents to be accessed through telephones 116 AND 118. WML can be used to communicate with wireless devices, such as cell phone 110. cHTML can be used to communicate with handheld devices, such as personal digital assistant (PDA) 112. Finally, HTML and XML can be used to communicate with a standard browser on computer system 114.

[0049] Note that a document can be written once in device-independent MXML form. The MXML document can then be translated into device-specific markup languages, such as HTML, XML, WML, HDML and VoiceXML. This can potentially save a considerable amount of programmer time because it is not necessary to write a different version of the application for each different markup language. It can also save on storage space because only a single version of the application needs to be stored.

[0050] While translating MXML document 104 into VoiceXML, transformation framework 102 can also facilitate translating a locale-independent symbolic representation of data to be outputted into a locale-specific voice output. This process is described below with reference to FIGS. 2-4. Note that during the translation process, transformation framework 102 can obtain a locale attribute that identifies a version of a language spoken in a particular locale. For example, the locale attribute “en-UK” can specify the version of the English language spoken in the United Kingdom. This locale attribute can then be used to generate a locale-specific voice output.

[0051] Note that transformation framework 102 can also receive voice input and can interpret the voice input using a locale-specific grammar.

[0052] Voice Gateway

[0053]FIG. 2 illustrates a voice gateway 106 in accordance with an embodiment of the present invention. Voice gateway 106 includes a VoiceXML browser 202, Automated Speech Recognition unit (ASR) 204, Text-To-Speech synthesis (TTS) engine 206, Dual Tone Multi-Frequency (DTMF) unit 208, media recording engine 210, media playback engine 212, and telephone interface 214.

[0054] VoiceXML browser 202 renders VMXL pages received from transformation framework 102 within application server 105.

[0055] Telephone interface 214 is used to access telephone network 216.

[0056] On the input side, ASR 204 recognizes voice input received from a user through telephone interface 214. Additionally, DTMF unit 208 can be used to recognize touchtone telephone signals through telephone interface 214. On the output side, TTS engine 206 converts textual output into a synthesized audio stream, prior to outputting the audio stream through telephone interface 214.

[0057] Media recording engine 210 can be used to record audio streams received from a user, while media playback engine 212 can be used to play back audio files for a user.

[0058] Voice Output

[0059] One challenge encountered by application developers is to output structured data in a format that is understood by users regardless of the locale. Structured data in this context can refer to any of a variety of data types ranging from “primitive datatypes” (i.e. integers, decimals, strings, characters, etc.) to more complex combinations of these “primitive datatypes” (e.g. dates, times, currencies, acronyms, flight numbers, etc.). Typically, each of these data types have some sort of symbolic or iconic representation that allows for abbreviated display in a user interface (UI) and a reduced amount of memory overhead for storage. For example, a simple counting application that needs to display one integer at a time may choose to do so by displaying the iconic value for each integer (1, 2, 3, 4, etc.) rather than the spelling of each integer (one, two, three, four, etc.). However, relying on iconic representations of this data yields several problems.

[0060] System developers rely on the user of an application to correctly interpret the iconic value as a particular datatype. For example, consider two different software applications. In the first, a message is visually displayed that reads: “I have 5 socks in my sock drawer.” The user is expected to see this and create a mental model of a sock drawer with five (5 as a cardinal number) socks in it. In the second application, a message is visually displayed that reads: “Today is Mar. 5, 2003.” In this case (at least for users in the United States), it is quite likely that the user will read this statement as “Today is March fifth (five as an ordinal number), two thousand three.” In some cases, the internal representation of the data (5) is the same, but the interpretation of that iconic information varies according to context.

[0061] Just as the interpretation of iconic information varies according to context, so too does the interpretation vary according to the cultural conventions of the locale in which the iconic information is being presented. For example, the interpretation of the statement “Today is Mar. 5, 2003.” in The United Kingdom will likely be: “Today is the third of May, two thousand three.” Here, the same iconic representation of a date in U.S. English and United Kingdom English has two entirely different meanings.

[0062] These issues do not pose very drastic problems for a graphical user interface (GUI), because people have been conditioned throughout their lives to associate the visual, iconic representations of numbers and other basic data types with their underlying meaning. However, in other types of user interfaces such as a voice interface, the user does not have the benefit of a graphical display on which an iconic representation is shown. Current text-to-speech converters cannot consistently interpret the input data and provide the proper, locale-specific output to the user that the application developer intended. Instead, the applications are typically rewritten and/or modified for each locale.

[0063] The present invention provides a framework for generating a locale-specific voice output for an application in accordance with an embodiment of the present invention. Referring to FIG. 3A, transformation framework 102 feeds data to be outputted into an intermediate interpreter 302. Note that this data to be outputted is in a symbolic form, which is language-independent and locale-independent.

[0064] Intermediate interpreter 302 feeds the data through expansion mechanism 304, which expands the data into a fully articulated locale-specific textual representation of the data. For example, if the locale attribute has the value “en-US” for the United States, the date “2003-02-04” (in language-independent ISO standard 8601 format YYYY-MM-DD) can be expanded into fully articulated textual form in US English as “February fourth, two thousand three.” On the other hand, if the locale attribute has the value “en-UK” for the United Kingdom, the date “2003-02-04” can be expanded into fully articulated textual form in UK English as “The fourth of February, two thousand three.” Note that changing the locale attribute can also cause the date to be translated into fully articulated text in other languages besides English.

[0065] After the symbolic representation of the data is expanded into a textual representation, intermediate interpreter 302 feeds it through an association mechanism 306, which associates the textual representation with one or more audio files containing locale-specific voice output corresponding to the textual representation. In doing so, association mechanism 306 attempts to match the largest possible substrings of the textual representation with corresponding audio files from a library. This generally results in the highest possible quality speech output.

[0066] Expansion Mechanism

[0067]FIG. 3B illustrates an expansion mechanism 304 in accordance with an embodiment of the present invention. Expansion mechanism 304 includes expander factory 312. During operation of the system, expander factory 312 creates a locale-specific expander upon demand for each locale that is involved in a conversion operation. For example, locale specific expanders 314, 316, and 318 are illustrated in FIG. 3B. Note that there can be more of fewer locale specific expanders than are shown in FIG. 3B.

[0068] In one embodiment of the present invention, the system includes an application programming interface (API) for the specific language, for example, a JAVA™ API. This API is independent of locale and thus allows an application developer to invoke the API in a consistent manner from an application.

[0069] For example, an application programmer may enter the command:

[0070] EXPAND(date(Mar. 5, 2003), en-US, DMY);

[0071] The system determines that the expansion of the data should conform to the US English locale, and should include the date, month, and year fields. If a US English locale specific expander is not currently instantiated, expander factory 312 instantiates locale specific expander 314 to expand data items for the US English locale.

[0072] Locale specific expander 314 then expands the date using the rules for expansion of dates in the US English locale and the requested fields. In this case, the date is rendered as: “March fifth, two thousand three.” Note that the fields can be used to yield different forms of the date. For example, the field “DaDM” could indicate that the day, date, and month are desired. In this case, the output would be “Wednesday, March fifth.” Note also that the order that the fields are listed does not change the order of the output. The order of the output is specified by the locale. If the fields are listed as “”MDDa,” the output is still “Wednesday, March fifth.”

[0073] As another example, if the application programmer enters the command:

[0074] EXPAND(date(Mar. 5, 2003), en-UK, DMY);

[0075] the system determines that the expansion of the data should conform to the United Kingdom English locale, and should include the date, month, and year fields. If a United Kingdom English locale specific expander is not currently instantiated, expander factory 312 instantiates locale-specific expander 316 to expand data items for the United Kingdom English locale. The date is then rendered as “The third of May, two thousand three.”

[0076] As a final example, if the application programmer enters the command:

[0077] EXPAND(date(Mar. 5, 2003), es-ES, DMY);

[0078] the system determines that the expansion of the data should conform to the Spanish locale, and should include the date, month, and year fields. If a Spanish locale specific expander is not currently instantiated, expander factory 312 instantiates locale specific expander 318 to expand data items for the Spanish locale. The date is then rendered as “tres de mayo, de dos mil tres.”

[0079] In another embodiment of the system, entry to the API can be through an invocation from a markup language. For example, the markup language invocation:

[0080] <SimpleSpeech say-as=“date” locale=“en-US” fields=“DMY”>

[0081] would call the API to convert the date into a US English text string including the date, month, and year fields.

[0082] In another embodiment, the conversion can be controlled though a cascading style sheet (css) where the locale and fields are pre-specified by the style. A date expansion would then be triggered by:

[0083] <css.date>Apr. 2, 2003</css>

[0084] This date is then expanded using the style sheet's locale and date fields. Note that while the above descriptions are for rendering dates, each locale specific expander includes methods for expanding other forms of iconic information. For example, the cardinal number 1,000,000,000 will be rendered as one billion in US English and as a thousand million in United Kingdom English.

[0085] Process of Generating Voice Output

[0086]FIG. 4 presents a flow chart illustrating the process of generating voice output in accordance with an embodiment of the present invention. The system starts by receiving data to be outputted from an application in a language-independent and locale-independent symbolic form (step 402). Next, the system obtains a locale attribute associated with the output (step 404). In one embodiment of the present invention, this locale attribute is encoded as an attribute within a VoiceXML document.

[0087] Next, the system feeds the symbolic form of the data into expansion mechanism 304, which expands the data into a fully articulated locale-specific textual representation (step 406).

[0088] This fully articulated textual representation then feeds into association mechanism 306, which associates the textual representation of the data with one or more audio files containing locale-specific voice output corresponding to the textual representation (step 408).

[0089] Finally, the system causes the audio files to be outputted to the user (step 410). This can be accomplished by sending references to the audio files (or the audio files themselves) from transformation framework 102 to voice gateway 106 (see FIG. 1). This allows voice gateway 106 to play the audio files through media playback engine 212 (see FIG. 2).

[0090] Process of Receiving Voice Input

[0091] Voice input to an application is typically facilitated through the use of “grammars,” which are codified representations of words/phrases/concepts that a user of the application may say to perform some action. There are a variety of different categories that these grammars can fall into—some are application-specific, and as such are defined at the application level by the software developer. These application-specific grammars may themselves fall into one or more categories depending on their behavior.

[0092] For example, certain types of grammars can be considered “command and control” since they are grammars that specify a limited number of short command phrases that map to a particular action or concept. These kinds of grammars are often written inline with the rest of the application code. There are also more “conversational” or “natural language” grammars, which allow for a much wider range of user input to be recognized as the same concept. The ostensible benefit of “conversational” grammars over the simpler “command and control” type grammars is that users of the “conversational” interface do not have to learn special commands to interact with the service; indeed, in a well-implemented “conversational” application, the user should be able to speak as freely as if they were speaking with another human being.

[0093] Another kind of grammar is not application specific, but rather represents a common set of functionality across many applications. For example, many classes of voice applications require certain basic input capabilities to allow users to enter things like numbers, dates, times, etc. These types of input mechanisms are so common in fact, that the VoiceXML specification identifies a number of these common input mechanisms as “built-in” grammars, which all VoiceXML interpreters need to treat in a consistent way.

[0094] The main problem that arises from the VoiceXML built-in grammars is that the VoiceXML specification does not completely specify how the various grammar types are to be handled. In particular, the specification says nothing about the actual set of input phrases that should be matched for any built-in grammar type. Instead, the specification primarily defines the return format that the built-in grammar handlers should send to the application upon matching an utterance. This lack of definition proves to be problematic for two reasons. First, the absence of a defined set of input phrases for each built-in grammar type means that different VoiceXML gateways can accept different sets of input from users, thus undermining the goal of application portability even for a single language. Second, the specification provides little direction about how built-in grammars should deal with other languages, saying simply that “the set of accepted spoken input for each built-in type is platform dependent and will vary by language.”

[0095] In order to address the various issues raised by voice input internationalization, one embodiment of the present invention provides a standardized set of built-in grammars as part of a Voice Globalization Framework. These grammars fully specify the set of phrases that can be recognized for a particular datatype, thus ensuring consistency of user experience across different VoiceXML gateways. Additionally, the built-in grammars are implemented for each locale, so that consistency is accomplished not just across gateways, but across all locales. Furthermore, the interface to the developer is simple and unified—on any given form field, the developer simply provides attributes pertaining to the “type” of grammar to invoke as well as a locale identifier.

[0096]FIG. 5 illustrates the process of receiving voice input in accordance with an embodiment of the present invention. While constructing a VoiceXML document 502, transformation framework 102 (from FIG. 1) replaces a specifier for a datatype with a Uniform Resource Identifier (URI) 504, which can be used to determine a location for a locale-specific grammar 506 in library 505. Note that library 505 can include a number of different locale-specific grammars for each datatype.

[0097] Next, transformation framework 102 sends VoiceXML document 502 to Automated Speech Recognition unit (ASR) 204 within voice gateway 106 (see FIG. 2). This causes ASR 204 to load locale-specific grammar 506 from library 505. ASR 204 then uses locale-specific grammar 506 to interpret a voice input 510 from a user 512. This results in a translation 508 of voice input 510 into a symbolic form for the associated datatype.

[0098] Note that if locale-specific grammar 506 is small enough, locale-specific grammar 506 can be inserted “in-line” into VoiceXML document 502. This eliminates the need for ASR 204 to load locale-specific grammar 506 from library 505.

[0099] In one embodiment of the present invention, the locale-specific grammar 506 identifies a standard set of phrases to be recognized by the speech recognition engine while receiving voice input for the datatype. In particular, a given locale-specific grammar can associate one or more phrases that can be spoken with a corresponding semantic meaning. For example, a grammar can associate the phrases “goodbye,” “exit,” “see ya,” “log off” and “later” with a command to exit from a program.

[0100] In an effort to standardize grammars for speech recognition, a number of gateway providers have developed systems that adhere to the Speech Recognition Grammar Specification (SRGS) standard. Unfortunately, there are many inconsistencies between different voice gateway implementations of the SRGS standard. In order to remedy this problem, one embodiment of the present invention uses a common subset of SRGS, which is compatible with the different voice gateway implementations. This “subset” technique can be used to achieve compatibility with a number of voice gateway implementations.

[0101] However, other voice gateway implementations remain incompatible even with a subset of SRGS. For these voice gateway implementations, the voice gateway provider can write a gateway-specific driver that can be incorporated into transformation framework 102. For example, referring to FIG. 6, a gateway driver X 602 can be added to a base voice transformer 604 to produce a gateway-specific transformer for voice gateway X 606. Similarly, a gateway driver Y 612 can be added to the base voice transformer 604 to produce a gateway-specific transformer for voice gateway Y 616.

[0102]FIG. 7 presents a flow chart illustrating how a system is configured to receive voice input in accordance with an embodiment of the present invention. The system starts by receiving a VoiceXML document 502 (step 702). Next, the system obtains a locale attribute for the document (step 704). In one embodiment of the present invention, this involves retrieving the locale attribute from VoiceXML document 502 itself. Note that it is possible to obtain this locale attribute from an eternal source outside of VoiceXML document 502.

[0103] Next, while scanning through VoiceXML document 502, the system encounters a datatype for which there exists a pre-defined grammar (step 706). The system then uses the locale attribute to look up a locale-specific grammar for the datatype (step 708). Next, the system inserts a URI 504 for the locale-specific grammar into VoiceXML document 502, wherein URI 504 can be used to determine a location for the grammar (step 710). Alternatively, the system can insert the locale-specific grammar itself into VoiceXML document 502.

[0104] Finally, the system sends VoiceXML document 502 to a voice gateway 106 (step 712). This causes ASR 204 within voice gateway 106 to load the locale-specific grammar (step 714). This allows ASR 204 to use the locale-specific grammar while subsequently interpreting voice input from a user (step 716).

[0105] The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims. 

What is claimed is:
 1. A method for recognizing voice input, comprising: receiving a document that includes a specification of a datatype for which there exists a predefined grammar; obtaining a locale attribute for the datatype, wherein the locale attribute identifies a version of a language that is spoken in a locale; using the locale attribute to lookup a locale-specific grammar for the datatype; and communicating the locale-specific grammar to a speech recognition engine, thereby allowing the speech recognition engine to use the locale-specific grammar in recognizing a voice input for the datatype.
 2. The method of claim 1, wherein the document that includes the specification of the datatype is a Voice eXtensible Markup Language (VoiceXML) document.
 3. The method of claim 2, wherein obtaining the locale attribute involves obtaining the locale attribute from the VoiceXML document.
 4. The method of claim 1, wherein the locale attribute is encoded in an application markup language.
 5. The method of claim 1, wherein the document that includes the specification of the datatype is an MXML document which is used to generate a VoiceXML document.
 6. The method of claim 1, wherein obtaining the locale attribute involves receiving the locale attribute as an application parameter.
 7. The method of claim 1, wherein obtaining the locale attribute involves receiving the locale attribute as an application parameter associated with a particular user.
 8. The method of claim 1, wherein the locale-specific grammar identifies a standard set of phrases to be recognized by the speech recognition engine while receiving voice input for the datatype.
 9. The method of claim 1, wherein the locale-specific grammar associates a phrase that can be spoken with a corresponding semantic meaning.
 10. The method of claim 1, wherein communicating the locale-specific grammar to the speech recognition engine involves communicating a reference to the speech recognition engine, wherein the reference specifies where the locale-specific grammar can be retrieved from.
 11. The method of claim 1, wherein communicating the locale-specific grammar to the speech recognition engine involves incorporating the grammar “in-line” into a VoiceXML document, and then communicating the VoiceXML document to the speech recognition engine.
 12. The method of claim 1, wherein the locale attribute includes: a language code that identifies the language; and a region code that identifies a geographic region in which a locale-specific version of the language is spoken.
 13. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for recognizing voice input, the method comprising: receiving a document that includes a specification of a datatype for which there exists a predefined grammar; obtaining a locale attribute for the datatype, wherein the locale attribute identifies a version of a language that is spoken in a locale; using the locale attribute to lookup a locale-specific grammar for the datatype; and communicating the locale-specific grammar to a speech recognition engine, thereby allowing the speech recognition engine to use the locale-specific grammar in recognizing a voice input for the datatype.
 14. The computer-readable storage medium of claim 13, wherein the document that includes the specification of the datatype is a Voice eXtensible Markup Language (VoiceXML) document.
 15. The computer-readable storage medium of claim 14, wherein obtaining the locale attribute involves obtaining the locale attribute from the VoiceXML document.
 16. The computer-readable storage medium of claim 13, wherein the locale attribute is encoded in an application markup language.
 17. The computer-readable storage medium of claim 13, wherein the document that includes the specification of the datatype is an MXML document which is used to generate a VoiceXML document.
 18. The computer-readable storage medium of claim 13, wherein obtaining the locale attribute involves receiving the locale attribute as an application parameter.
 19. The computer-readable storage medium of claim 13, wherein obtaining the locale attribute involves receiving the locale attribute as an application parameter associated with a particular user.
 20. The computer-readable storage medium of claim 13, wherein the locale-specific grammar identifies a standard set of phrases to be recognized by the speech recognition engine while receiving voice input for the datatype.
 21. The computer-readable storage medium of claim 13, wherein the locale-specific grammar associates a phrase that can be spoken with a corresponding semantic meaning.
 22. The computer-readable storage medium of claim 13, wherein communicating the locale-specific grammar to the speech recognition engine involves communicating a reference to the speech recognition engine, wherein the reference specifies where the locale-specific grammar can be retrieved from.
 23. The computer-readable storage medium of claim 13, wherein communicating the locale-specific grammar to the speech recognition engine involves incorporating the grammar “in-line” into a VoiceXML document, and then communicating the VoiceXML document to the speech recognition engine.
 24. The computer-readable storage medium of claim 13, wherein the locale attribute includes: a language code that identifies the language; and a region code that identifies a geographic region in which a locale-specific version of the language is spoken.
 25. An apparatus that recognizes voice input, comprising: a receiving mechanism configured to receive a document that includes a specification of a datatype for which there exists a predefined grammar; wherein the receiving mechanism is additionally configured to obtain a locale attribute for the datatype, wherein the locale attribute identifies a version of a language that is spoken in a locale; a lookup mechanism configured to use the locale attribute to lookup a locale-specific grammar for the datatype; and a communication mechanism configured to communicate the locale-specific grammar to a speech recognition engine, thereby allowing the speech recognition engine to use the locale-specific grammar in recognizing a voice input for the datatype.
 26. The apparatus of claim 25, wherein the document that includes the specification of the datatype is a Voice eXtensible Markup Language (VoiceXML) document.
 27. The apparatus of claim 26, wherein the receiving mechanism is configured to obtain the locale attribute from the VoiceXML document.
 28. The apparatus of claim 25, wherein the locale attribute is encoded in an application markup language.
 29. The apparatus of claim 25, wherein the document that includes the specification of the datatype is an MXML document which is used to generate a VoiceXML document.
 30. The apparatus of claim 25, wherein the receiving mechanism is configured to obtain a locale attribute as an application parameter.
 31. The apparatus of claim 25, wherein the receiving mechanism is configured to obtain a locale attribute as an application parameter associated with a particular user.
 32. The apparatus of claim 25, wherein the locale-specific grammar identifies a standard set of phrases to be recognized by the speech recognition engine while receiving voice input for the datatype.
 33. The apparatus of claim 25, wherein the locale-specific grammar associates a phrase that can be spoken with a corresponding semantic meaning.
 34. The apparatus of claim 25, wherein the communication mechanism is configured to communicate the locale-specific grammar to the speech recognition engine by communicating a reference to the speech recognition engine, wherein the reference specifies where the locale-specific grammar can be retrieved from.
 36. The apparatus of claim 25, wherein the communication mechanism is configured to communicate the locale-specific grammar to the speech recognition engine by incorporating the grammar “in-line” into a VoiceXML document, and then communicating the VoiceXML document to the speech recognition engine.
 37. The apparatus of claim 25, wherein the locale attribute includes: a language code that identifies the language; and a region code that identifies a geographic region in which a locale-specific version of the language is spoken.
 38. The apparatus of claim 25, wherein apparatus is located within an application server; and wherein the speech recognition engine is located within a voice gateway.
 39. A means for recognizing voice input, comprising: a receiving means for receiving a document that includes a specification of a datatype for which there exists a predefined grammar; wherein the receiving means is additionally configured to obtain a locale attribute for the datatype, wherein the locale attribute identifies a version of a language that is spoken in a locale; a lookup means that uses the locale attribute to lookup a locale-specific grammar for the datatype; and a communication means for communicating the locale-specific grammar to a speech recognition engine, thereby allowing the speech recognition engine to use the locale-specific grammar in recognizing a voice input for the datatype. 